Refresh Aurora 7.2 candidate to merged PR 139 source - #359

Summary

• Refresh unified72 to merged Aurora PR Battery: energy by app, charging/standby stats, health trend, alerts, report #139 (644133b7799f759c5bfd88507b6246d298b6509c), with immutable archive verification and separate 7.2.10-elementary-aurora72-wip2 package/module identity. Retire the already-upstream bindgen patch while retaining provenance.
• Owner approved checked staging, then one-shot arming conditional on passing repeat CI. Wip2 has now booted on J314S and matches its audited Image/live build ID. One-shot consumed; .20 remains persistent default. Old fallback files and shared boot.bin remain unchanged.
• Retain legacy shared DTBs, exact Arch unlock image semantics and 91 byte-verified early modules. Package/source/toolchain/config/licenses and root-private backups retained.

Build and source evidence

• Native ARM64 Image/modules/DTBs/package build/inspection/upload passed with unchanged .20 control in run 39595756051 at b21399953faa576b17f3121087742fb597c872a5. Independent original artifact audit verified ZIP/SHA256SUMS, complete corresponding source tree, package boundaries and J314S DTB.
• Both repeat matrix jobs passed run 39601423970 at ed08d502d294f6fa8c9160852e91f6f2ff5c802e. Subsequent receipts/docs preserve the kernel builder, manifest and native workflow inputs; installed bytes remain the original audited package.
• 71 repository tests passed before staging. Legacy DART 50, firmware 63, Bluetooth 46 and tunnel host controls retained. DCP 55/56 initial plus original USB Kconfig producer four-case rerun with corrected output path; stale DART-range host fixture port 12-pass, production source unchanged. Initial fixture failures and scope retained.
• Manual triage of 24 mechanical mismatches: 19 described source contracts retained, five open/partial. The other 40 reverse checks remain mechanical evidence. Full 64-fix semantic qualification remains open.

Actual first-boot results

Report and receipts bind this exact boot and runtime parameters.

• Live build ID e33ad2aa657320824a246a3b04814accdb31df1e matches staged Image; package/all 91 early modules verify. Runtime 37 DART providers retain one-cell bindings and observed firmware 13.5.0. New packaged DTB is an on-disk asset, not selected for boot.
• Scoped five-minute boot, PMP ready/ownership and CPU idle-counter checks pass.
• Actual Apple M1 Pro G13S C0 GPU shader/16-pixel RGBA readback passes on Mesa 26.0.8; 1 MiB temporary-file fsync/SHA256 readback passes.
• Owner confirms internal display/input. Compositor observes internal 3024x1964/120Hz and external DP-1 1920x1080/60Hz later in the boot.
• Current physical port result: owner confirms dock picture on all three ports; front-left and right also have explicit input confirmation. Rear-left initially stayed blank and later recovered. The later confirmations supersede the initial failure. Retained timing receipts include the owner-corrected rear-left label and the front-left detection-boundary correction.
• Pilot partner-detection to compositor-active timings: right 4.486 s, rear-left 4.509 s, front-left 4.511 s (corrected from retained events). These are single moves with 0.5 s sampling, not a port ranking or cable-to-pixels measurement. Logs show link-training retries; do not establish a new 7.2 regression from unequal traces. Prior .20-enh1 also had AT-register retries.
• Selected severe-log scan through post-smoke snapshot found no panic/oops/lockup/I/O-error patterns. Firmware warnings also occurred on prior kernel and remain documented separately. Raw logs remain private.

Remaining acceptance

Incomplete qualification; no stable promotion. Next repeated matched latency trials and owner-controlled return to normal default .20 for actual recovery, before suspend/power work. Unknown PowerSaveMode/display context stays unknown. Startup/owner hotplug power is uncontrolled; no idle baseline, A/B or savings claim. No automated re-arm, reboot, boot.bin rewrite, service restart or runtime-parameter change.

Saved maintenance task stays paused/on-demand; next maintenance task has not started. Earlier maintenance checkpoint is separate in #358.

Integration and upstream review

• Merged current dev through f8ce244, preserving both handoff histories. Builder, unified72 manifest and native workflow remain byte-identical to the audited build inputs.
• Reviewed canonical omacom/linux-aurora integration and WIP. No local dock driver patch to upstream: active patch list is empty. A host-only DART range fixture compatibility patch remains a concrete candidate; source hashes, current-branch comparison and prior partial PR Display profiles: restore built-in-only layout after unplug, log Gala's response time #64 are retained in UPSTREAM-CANDIDATES.md. No upstream issue, comment or PR was published.
• Latest-head CI runs are separate from the successful repeat build; do not imply those runs passed while pending.